Multimedia Message Delivery in a Communication System

ABSTRACT

A method and system of delivering a Multimedia Messaging Service (MMS) message is disclosed. In one example, the method includes providing a storage location and time duration for outside content to be indirectly referenced by an MMS message. Receiving and storing the outside content via a transport network is also disclosed. The method may include encapsulating an MMS message in a payload of a transport message with the MMS message indirectly referencing the storage location of the outside content. Delivery of the transport message may occur over a transport network. Confirming receipt of the transport message is also disclosed.

RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 13/118,008, filed May 27, 2011 and titled “Methodand System for Multimedia Message Delivery in a Communication System,”which in turn is a continuation of U.S. patent application Ser. No.10/964,911, filed Oct. 13, 2004 and titled “Method and System forMultimedia Message Delivery in a Communication System,” which claimspriority to U.S. Provisional Pat. App. No. 60/510,654, filed Oct. 13,2003, the disclosures of which are hereby incorporated herein byreference in their entirety. This application is also related to U.S.patent application Ser. No. 10/920,850, filed on Aug. 18, 2004, which ishereby incorporated by reference in its entirety.

BACKGROUND

Data transfer, including wireless and wireline messaging, is a servicethat has become increasingly important to subscribers. Existing serviceproviders, such as providers of wireless and wireline voice services, aswell as companies catering specifically to wireless data needs, providedata services and plans. Some subscribers may obtain a data package thatis part of a total package that may include wireless voice services andother services. Other subscribers, for example those using a personaldigital assistant (PDA) that is not equipped to accept voice calls, mayrequire only wireless data services.

Existing networks allow users of devices such as wireless phones, twoway pagers, and computers to exchange simple text based messages withother subscribers and, in some cases, with users who may not be a partof the same network or who may only have access to traditionallyland-based services such as email. The complexity of the type ofmessages being sent, as well as the content of the messages, hasincreased as the sophistication of the networks has increased. Forexample, newer wireless and wireline networks generally provide supportfor the exchange of photographs and multimedia presentations betweenwireless users and between wireless users and wireline users.

Networking and wireless standards have been developed to providefunctionality for multimedia capable devices and to allow interactionbetween the new devices and legacy devices and systems. For example,application servers have been introduced into networks under the 3GPP2and 3GPP standards, such as internet protocol (IP) multimedia subsystem(IMS) based networks, to support multimedia applications andcommunications. However, despite these developments, existing standardsand technologies have failed to adequately address all of the technologyneeds brought on by the data transfer requirements of the multimediacapable devices.

SUMMARY

In one or more embodiments, the present disclosure introduces a methodfor communicating using a Multimedia Messaging Service (MMS) over aSession Initiated Protocol (SIP) based network. The method includesreceiving a first SIP message request over the SIP based network, andsending a first SIP message response over the SIP based network. Themethod also includes processing a message payload of the first SIPmessage request. The message payload may contain MMS content. The methodmay also include determining that the message payload contains auniversal resource indicator (URI) which provides an indirect referenceto content outside the SIP message. The method may include accessing theoutside content from a predetermined location indicated by the URI.

In one or more embodiments, the present disclosure introduces a methodof delivering an MMS message that includes providing a storage locationand duration for outside content to be indirectly referenced by an MMSmessage. The outside content may be received from a transport networkand stored. An MMS message may be encapsulated in a payload of atransport message, and the MMS message may indirectly reference thestorage location of the outside content. The transport message may bedelivered over the transport network and confirmation of receipt of thetransport message may be sent.

Embodiments for a system for delivery of MMS message are also disclosed.The system may comprise a user agent configured to send and receiveMultipurpose Internet Mail Extension (MIME) encoded MMS messages over atransport network in a payload of a transport message. The system mayalso include an MMS Relay/Server configured to send and receive MIMEencoded MMS messages over the transport network in a payload of atransport message. The user agent and the MMS Relay/Server may each beconfigured to provide a confirmation of receipt of a transport message.The MMS Relay/Server may also be configured to provide a storagelocation for content indirectly referenced by an MMS message that isencapsulated in a transport message when the MMS message is greater thana predetermined size.

The foregoing has outlined features of several embodiments so that thoseskilled in the art may better understand the detailed description thatfollows. Additional features will be described below that may furtherform the subject of the claims herein. Those skilled in the art shouldappreciate that they can readily use the present disclosure as a basisfor designing or modifying other processes and structures for carryingout the same purposes and/or achieving the same advantages of theembodiments introduced herein. Those skilled in the art should alsorealize that such equivalent constructions do not depart from the spiritand scope of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a message flow chart corresponding to one embodiment of amethod of transporting Multimedia Messaging Service (MMS) messages overa Session Initiation Protocol (SIP) based network.

FIG. 2 is a block diagram of one embodiment of an SIP message with anMMS message payload.

FIG. 3 is a block diagram of another embodiment of an SIP message withan MMS message payload.

FIG. 4 is a message flow chart corresponding to a method for determininga storage location for content indirectly referenced in an MMS message.

FIG. 5 is a message flow chart corresponding to a method for placingmultimedia content onto an MMS Relay/Server.

FIG. 6 is a flow chart illustrating another embodiment of a method fortransporting MMS messages on an SIP based network.

FIG. 7 illustrates a block diagram of one embodiment of a wirelessnetwork within which aspects of the present disclosure may beimplemented.

DETAILED DESCRIPTION

It is to be understood that the following disclosure provides manydifferent embodiments, or examples, for implementing different featuresof various embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting. Inaddition, the present disclosure may repeat reference numerals and/orletters in the various examples. This repetition is for the purpose ofsimplicity and clarity and does not in itself dictate a relationshipbetween the various embodiments and/or configurations discussed.

The present disclosure is related to, and hereby incorporates, MMS MMIStage 3 Using SIP, available athttp://www.3gpp2.org/Public_html/specs/under the document nameX.50016-312-0 v1.0. However, it is understood that the presentdisclosure may be applied to any application server (AS) operating in anInternet protocol (IP) multimedia subsystem (IMS) network as defined,for example, under the 3GPP and 3GPP2 standards. For purposes ofillustration, the present disclosure frequently uses the MultimediaMessaging Service (MMS) standard as a particular example of a SessionInitiation Protocol (SIP) AS, but it is understood that the disclosureis not limited to MMS and may be applied to other SIP applicationservers, as well as other IMS application servers. Furthermore, as SIPmay be used to provide a transport layer-independent way to exchangedata and provide other services, such as voice or phone services, thepresent disclosure is equally applicable to both wireless and wirelineservices. Accordingly, while SIP and MMS specific messages and messagesequences are described in the following examples, it is understood thatthey may be replaced by other messages and message sequences forimplementations involving other technologies.

Referring to FIG. 1, a message flow chart corresponding to oneembodiment of a method of transporting Multimedia Messaging Service(MMS) messages over a Session Initiation Protocol (SIP) network isillustrated. A Multimedia Messaging Service (MMS) User Agent (UA) 102 isshown in communication with an MMS Relay/Server 106. It is understoodthat the MMS UA 102 may not be in direct communication with the MMSRelay/Server 106, as other network components may interpose the MMS UA102 and the MMS Relay/Server 106.

The MMS UA 102 (which may be viewed as an MMS implementation of anApplication User Agent (AUA) for any wireless or wireline IMS user)enables a wireless user to access MMS services. The MMS UA 102 may beimplemented by hardware, software, firmware, or another suitable mediumand may reside on a wireless mobile device. A wireless mobile device mayinclude a mobile phone or other wireless enabled devices, such as aPersonal Digital Assistant (PDA), a personal computer, an automobile, ora two-way paging device, for example. Other devices on which an MMS UA102 may reside include workstations, servers, a network node, or othernetwork, computer, or telecommunications systems or components. In someembodiments, the MMS UA 102 may communicate directly with the MMSRelay/Server 106. In some embodiments, for example where the MMS UA 102resides on a wireless mobile device, there may be interposing structuresand equipment, as explained in greater detail below.

The MMS UA 102 may communicate with the MMS Relay/Server 106 via atransport network. The transport network may include all or portions ofwireless or wireline phone networks, distributed networks such as theInternet, wide area networks (WANs), local area networks (LANs), and/orother communications networks. In one embodiment, the MMS UA 102 and theMMS Relay/Server 106 communicate over an SIP-based network In someembodiments, there may be additional SIP devices or nodes associatedwith the SIP Relay/Server 106, such as an SIP registrar (not shown), anSIP proxy server (not shown), or an SIP redirect server (not shown). TheSIP network itself may implemented independently of the transport layer,which may be based on Internet Protocol (IP), User Datagram Protocol(UDP), Transmission Control Protocol (TCP), and/or other standards. TheSIP-based network may be implemented as a public network (e.g., theInternet), as a private network (e.g., an intranet), or as a combinationof public and private networks.

The MMS Relay/Server 106 may provide multimedia messaging services tothe MMS UA 102. In some embodiments, an SIP Proxy (not shown) may serveto relay information from the MMS Relay/Server 106 to the MMS UA 102.The MMS Relay/Server 106 may either act as a server and route MMSmessages from one MMS UA to another, or may act as a relay, possibly incommunication with other MMS Relay/Servers, to provide messaging orother services over an SIP based network.

In operation, a multimedia message may be sent via one or more SIPmessages as shown by the MM1_submit.REQ label 110 of FIG. 1. An SIPmessage request 112 may be sent from the MMS UA 102 to the MMSRelay/Server 106 over the SIP network. The SIP message request 112 maycontain an embedded or encapsulated MMS message as will be described ingreater detail below. Upon receiving the SIP message request 112, theMMS Relay/Server 106 may confirm receipt of the SIP message request 112by sending an SIP message response 114 back to the MMS UA 102. Theresponse 114 may be an SIP “200 OK” message, for example. A confirmationof receipt of the MMS message, shown by MM1_submit.RES label 120, may besent from the MMS Relay/Server to the MMS UA 102 through another seriesof SIP messages. An SIP message request 122 containing the MMSconfirmation may be sent to the MMS UA 102 from the MMS Relay/Server106, followed by an SIP response 124 from the MMS UA 102 to the MMSRelay/Server 106. As before, the SIP response 124 may be an SIP “200 OK”response or other suitable SIP response.

Referring to FIG. 2, a block diagram of one embodiment of an SIP message200 with an MMS message payload is shown. The SIP message 200 is oneembodiment of message 112 of FIG. 1. The SIP message 200 may contain anSIP header 210. The SIP message may also contain a payload 212, whichmay encapsulate the MMS data. The payload 212 may be encoded inMultipurpose Internet Mail Extension (MIME) multipart/related format, oranother suitable format. Additionally, the payload may contain multipleparts. For example, the MMS content or payload 212 may have a headerfield 220 and a data field 225. The header field 220 may specifyinformation concerning the encapsulated MMS message, such as the contenttype. More information concerning the MMS format may be found in thedocument, OMA-WAP-ENC-V1.1 Multimedia Messaging Service; EncapsulationProtocol, available at http://www.openmobilealliance.org/, which ishereby incorporated by reference.

As denoted by block 225 of FIG. 2, the payload 212 may also contain theactual content of the MMS message 225 or an indirect reference to thecontent, which may be located elsewhere on the network. When the MMSmessage 212 is processed by the MMS Relay/Server 106, the reference tothe MMS content may be through the use of a Uniform Resource Indicator(URI) or by other suitable means. Allocation of a URI for MMS content bythe MMS Relay/Server 106 will be described in greater detail below.

Referring to FIG. 3, a block diagram of another embodiment of an SIPmessage 300 with an MMS message payload is illustrated. The SIP message300 illustrates one embodiment of the SIP message request 122 of FIG. 1.The SIP message 300 may contain an SIP header 310, as before. Thepayload of the SIP message 300 may be an encapsulated MMS message 322,which may be encoded in MIME or another format. The actual content 322of the MMS message may be an MMS message confirmation. This confirmationcould be in response to the MMS message 212 of FIG. 2, which may be thepayload of the original SIP message request 112 of FIG. 1.

Referring to FIG. 4, a message flow chart 400 corresponding to a methodfor determining a storage location for content indirectly referenced inan MMS message is illustrated. As stated previously, an MMS message mayindirectly reference message content via a URI or other addressingmethod. The methods shown in FIGS. 4-5 for requesting storage andplacing content, respectively, may need to be performed before theprocedure for sending an MMS message (as shown in FIG. 1) to ensure thatthe referenced MMS content is available at the MMS Relay/Server. Themaximum size of the MMS message itself (without indirect referencing)may be limited by the provider of the transport network or otherconstraints. For example, the maximum size of an MMS message may be 1300bytes.

In a case where the MMS message provides an indirect reference, the MMSUA 402, which may be similar to the MMS UA 102 of FIG. 1, may send anSIP message request 410 to the MMS Relay/Server 406, which may besimilar to the MMS Relay/Server 106 of FIG. 1. The SIP message request410 may request a particular storage size and minimum length of timethat the storage location is reserved for the MMS content for example.The MMS Relay/Server 406 may respond to the MMS UA 102 by an SIPresponse message 412, which may indicate a storage location for the MMScontent and the minimum amount of time reserved for storage.

Referring to FIG. 5, a message flow chart corresponding to a method 500for placing multimedia content onto an MMS Relay/Server is shown. TheMMS UA 502 and the MMS Relay/Server 506 may be similar to those alreadydescribed. The method 500 of placing MMS content may be used inconjunction with the method 400 of FIG. 4 for determining a storagelocation for MMS content. Following the determination of a storagelocation for the indirectly referenced content, the MMS UA 502 may sendthe content to the MMS Relay/Server 506 via Hypertext Transfer Protocol(HTTP) or another method or protocol. An HTTP “PUT” command 510 mayissue from the MMS UA 502 to the MMS Relay/Server 506 specifying thestorage location for the content (from the request shown in FIG. 4) andmay provide the actual content. The MMS Relay/Server 506 may reply withan HTTP “200 (OK)” response 512. Following this procedure, MMS contentthat is indirectly referenced by an MMS message may be accessible on thesame MMS Relay/Server as the received MMS message.

In one embodiment of the present disclosure, when the MMS content hasbeen placed on the MMS Relay/Server, the content may be indirectlyreferenced by URIs in multiple MMS messages. The MMS content may only beaccessible to MMS messages or applications residing on the same MMSRelay/Server as the originally-received MMS message. In otherembodiments, the MMS content may be passed to other SIP basedapplications residing in different locations by passing the URI. Forexample, a SIP based application operated by a first service providermay be able to access message content stored by a second serviceprovider by using the URI referring to a storage location of the messagecontent.

Referring to FIG. 6, a flow chart 600 illustrating one embodiment of amethod for transporting MMS messages on an SIP based network is shown.If the MMS message to be sent will have an indirect reference to MMScontent as determined in step 601, a storage location is requested forthe content at step 605. When the storage location is received at step610, the content is placed on the MMS Relay/Server at step 615 andplacement is confirmed at step 620. The procedure for determining astorage location and placing the content (steps 605, 610, 615, and 620)was previously described in detail with regard to FIGS. 4-5.

If no indirect reference in the MMS message is needed (as determined instep 601), or following the confirmation of placement of the content atstep 620, a SIP message is sent at step 640 that encapsulates the MMSmessage as previously described. When the SIP message of step 640 isconfirmed at step 645, an SIP message containing an MMS confirmation maybe sent back to the original sender at step 650. Finally, the SIPmessage of step 650 may be confirmed at step 655. The process of sendingthe MMS message encapsulated in an SIP message (steps 640, 645, 650,655) was previously described in detail with regard to FIG. 1.

FIG. 7 illustrates a block diagram of a telecommunications network 700that provides an exemplary system within which the methods disclosedherein may be practiced. In the present example, the network 700 is awireless network that supports both voice and data packet communicationsusing General Packet Service Radio (GPRS) and Universal MobileTelecommunications System (UMTS) technologies.

The network 700 comprises a Radio Access Network (RAN) 751 and a corenetwork 752. The core network further comprises a circuit domain 753 anda packet domain 754. Other networks may be accessible to the network700, such as a Public Switch Telephone Network (PSTN) 755 (connected tothe circuit domain 753) and Internet 756.

The RAN 751 includes a plurality of cells (not shown) serviced by basetransceiver stations (BTS) 758, 759, and 760. The BTS 758 is connectedto a base station controller (BSC) 761 to provide a second-generationwireless network. The BTSs 759, 760 are accessible to radio networkcontrollers (RNC) 762, 763, respectively, to provide a third-generationwireless network. A mobile switching center/visitor location register(MSC/VLR) 764 may be used to connect the core network 753 with othernetworks, such as the PSTN 755. A home location register (HLR) 765 maybe accessible to the MSC/VLR 764 and also to a serving GPRS support node(SGSN) 766 and a gateway GPRS support node (GGSN) 767 in the packetdomain 754.

The network 700 enables at least one mobile device 768 to establish acommunication session with another device via the BTS 758. An MMS UA, aspreviously described, may reside on the mobile device 768. A request toestablish a communication session by the mobile device 768 may bedirected by the MSC/VLR 764 to (1) a second mobile device 769, (2) avoice terminal (not shown) coupled to the PSTN 755, or (3) a dataterminal (not shown) coupled elsewhere to the telecommunications network700. For example, if the communication session is a circuit datatransfer session, the request may be to connect the mobile device 768 toa computer or other data device via the network 700. If thecommunication is a packet data transfer session, the request may berouted through the SGSN 766, the GGSN 767, and to the Internet 756. AnSIP based network may interface with the SGSN 766 and/or the GGSN 767.It is noted that the mobile devices 768 and 769, while illustrated asmobile telephones, may be any mobile device capable of communicating viathe network 700.

An SIP Registrar/SIP Proxy 770 may be connected to the Internet 756 andmay utilize the Internet 756 using SIP over an IP transport layer.Similarly, an MMS Relay/Server 772 may be connected to the Internet 756using SIP with the Internet 756 as the IP transport layer. The SIPRegistrar/SIP Proxy 770 and the MMS Relay/Server 772 may operate bothwith one another, and with the MMS UA residing on the mobile device 768.It is understood that the network 700 is for purposes of illustrationand the present disclosure may be equally applicable to other networks,including code division multiple access (CDMA), time division multipleaccess (TDMA) networks, and third generation wireless networks using SIPfor both data and voice channels.

Those skilled in the art should appreciate that they may readily use thepresent disclosure as a basis for designing or modifying other processesand structures for carrying out the same purposes and/or achieving thesame advantages of the embodiments introduced herein. For example,various steps of the described methods and sequences may be executed ina different order or executed sequentially, combined, further divided,replaced with alternate steps, or removed entirely. In addition, variousfunctions illustrated in the methods or described elsewhere in thedisclosure may be combined to provide additional and/or alternatefunctions. Those skilled in the art should also realize that suchequivalent constructions do not depart from the spirit and scope of thepresent disclosure, and that they may make various changes,substitutions, and alterations herein without departing from the spiritand scope of the present disclosure.

What is claimed is:
 1. A method comprising: receiving at a MultimediaMessaging Service (MMS) a request for a storage location for storing MMScontent; identifying a storage location for the MMS content; and sendinga response to the request indicating the storage location.